I actually realized it here, but I think the API in general, needs bigger change. The reason does not have to do with new_static, it's rather new. The original idea, is that one can do either of the following:

#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc::new_static();

or:

#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc::new(buf_ptr, 1024 * 1024, true);

Even though we can mark new_static as const, there is not way we can mark new as const, since new calls an unsafe C function.

So personally I kinda wanted to simply remove new_static and new, and just wrap the following in a macro:

#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc{};

Simply put, I don't think it is a good API design if we simply put const on new_static, it works around the issue in some cases, but it does not touch the root problem

#[global_allocator]
static ALLOC: FixedAlloc = FixedAlloc{};

is fine. And call initialize function at the first time of malloc.